feat(checksum): Add multiple checksum configuration in goreleaser file#1739
Open
vagrawal-newrelic wants to merge 2 commits intomainfrom
Open
feat(checksum): Add multiple checksum configuration in goreleaser file#1739vagrawal-newrelic wants to merge 2 commits intomainfrom
vagrawal-newrelic wants to merge 2 commits intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a PR that include minor update in the go-releaser file that is creating 2 checksum file one for all the CLI binaries and the 2nd one for the install.sh file and the install.ps1 file.
This changes are done for the minor request that was asked by the customer(E.ON) in this WR.
Changes for the checksum generation and adding the install scripts to the GIT release assets was done as part of this PR.
No Test validation SS is available as there is no way to test the changes in local, a realtime release is required to test the changes..
Any further changes on this will be part of other PR and this PR will be attached in the new one to keep a track of the PR's that include all relevant changes to cater this WR.